Node / styrene-lab / omegon-armory.git / files / docs / public-launch-checklist.md

Displaying Rendered • View raw • Download

This checklist tracks the work required to move Omegon Armory from release candidate to public launch.

Publish the first public Armory release with:

• static catalog at T383838https://armory.styrene.io

• machine-readable API at T383838https://armory.styrene.io/api/index.json

• OCI artifacts at T383838ghcr.io/styrene-lab/omegon-armory/*

• enabled extension installs for entries that pass live install smoke tests

• clear documentation for staged candidates, self-hosting, and profile roadmap

Expected generated catalog:

T282828

Expected kinds:

T282828

Enabled extension gate:

T282828

External integration:

T282828

Staged but disabled candidates:

T282828

Run:

T282828

Pass criteria:

• all non-network tests pass

• site builds successfully

• generated API contains expected entry counts

Run with the release candidate Omegon binary:

T282828

Pass criteria:

• text plugin installs pass in a sandboxed T383838OMEGON_HOME

• catalog agent install checks pass where supported

• no local runtime state is committed

Run:

T282828

Pass criteria:

• every enabled extension installs by name

• T383838flynt passes

• T383838shuttle passes or is disabled before publication

• disabled candidates do not block launch

Decision rule:

T282828

Run or wait for:

T282828

Pass criteria:

• TOML validation passes

• OCI dry-run emits valid ORAS/cosign commands

• site build passes in Actions

• disabled/private staged repos do not fail reachability checks

Run manual workflow:

T282828

Pass criteria:

• GHCR login succeeds

• every artifact pushes

• T383838index:latest pushes

• cosign signing succeeds

• published index manifest fetch succeeds

• representative artifact manifest fetches succeed

Manual smoke commands:

T282828

Confirm GitHub secrets exist:

T282828

Push or manually dispatch T383838.github/workflows/site.yml.

Pass criteria:

T282828

Expected API count:

T282828

After site and OCI publish:

T282828

If Shuttle was disabled, verify it is not presented as an enabled install target:

T282828

Also verify OCI-backed packages are discoverable through the published index once Omegon has native Armory/OCI install support.

Launch is approved only when:

• local validation is green

• Actions validation is green

• OCI workflow published and smoke-tested

• Cloudflare Pages deployment is live

• enabled extension install smoke tests pass

• T383838shuttle is either proven installable or disabled

Immediately after public launch:

1. Fetch T383838https://armory.styrene.io/api/index.json and archive the response for release evidence.

2. Pull T383838ghcr.io/styrene-lab/omegon-armory/index:latest and verify it contains the same registry namespace.

3. Install each enabled extension from a clean T383838OMEGON_HOME.

4. Confirm docs pages render:

• T383838/docs/armory-operations/

• T383838/docs/oci-registry-stack/

5. Confirm no disabled candidates appear as installable public extension cards.

6. Open follow-up issues for any launch deferrals.

Not required for first public launch:

• profile artifacts in the live builder/site

• turnkey self-host compose stack

• OCI-backed extension binaries

• multi-index federation

• native Omegon OCI package installer

These are documented roadmap items, not launch blockers.

Production promotion tags are derived from the site package version and the promoted commit:

T282828

Example:

T282828

The package version is the release series, not a mandatory bump for every catalog-only change. This avoids blocking production promotion when generated catalog data changes without a hand-written site version bump. The tag remains immutable and unique per promoted commit.